<Server> Is not accesible. Remote procedure Failed
Hi,
My servers where working perfectly until I had to change the network card on the server I am currently having problems due to a unexpected powersurge inside the network. My main problem is that I can't access my shared folders through My Network Places.
I get:
\\<Server> is not accessible. You might not have permission to access this Network Resource. Contact the Administrator of this server to find out if you have access permisions.
The remote procedure call failed.
This happens only to my DC Server every other computer can access each other except this server. The odd thing is that I CAN do the following things:
-Still works as a DNS server.
-Domain Controller works fine.
-I was able to access another server mapping the folder with netuse.
-They do appear in the Network.
Things i CAN"T Do:
-Access through my Network places any other computer.
-Can't ping any other server. Not even Gateway.
-Other servers can't ping troublesome server, but can ping amongst them.
Even though I can access through mapped drives it is extremely slow and it is a small network of 3 servers. I do not have any firewalls installed they are all running windows server 2003 and they are all up to date. Any help would be extremely appreciated.
Thanks,
ShekerKa
August 9th, 2011 7:25pm
Hello,
for your DC, make sure that it points to its private IP address as primary DNS server. Once done, run
ipconfig /registerdns and restart netlogon on it.
Also, make sure that client computers are pointing to this DC as primary DNS server.
For ping requests, make sure that there is no firewall that is blocking ICMP traffic.
Also, make sure that you have no firewall / security software that is bloking traffic between your DC and client computers.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft Student
Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:
Security
Microsoft Certified Systems Engineer:
Security
Microsoft Certified Technology Specialist:
Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist:
Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist:
Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist:
Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise
Administrator
Microsoft Certified IT Professional: Server Administrator
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2011 7:50pm
I'm sorry but how do I "for your DC, make sure that it points to its private IP address as primary DNS server." It's been a while since I configure a DC.
August 9th, 2011 8:34pm
Please run ipconfig /all > ipconfig.txt and post the content of ipconfig.txt file.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft Student
Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:
Security
Microsoft Certified Systems Engineer:
Security
Microsoft Certified Technology Specialist:
Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist:
Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist:
Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist:
Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise
Administrator
Microsoft Certified IT Professional: Server Administrator
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2011 8:56pm
Mr X,
Thanks for all the help but I found the problem. Basically I was getting mixed signals from my network because due to the power surge that made me change ethernet cards it also blew out part of the PCI slot so that's why I could and couldn't
do some things that confirm a normal hardware and software connection. Thanks for all the advice.
ShekerKa
August 9th, 2011 10:02pm


